Does DOORS support version tracking?

TooDifficult - Mon Dec 13 16:20:58 EST 2010
Yes I do know of that, but the problem is that the powers that be want to keep that for big revisions.

I just want to know whether it's possible to trigger a new file save everytime the user presses save, like below:

0.0
0.1
0.2
0.3
1.0 ---- We would baseline this since the revision number changed but not the version number
1.1
1.2
1.3

Is there a method to get DOORS to save the file with the right hand number incremented?

Thanks,

TooDiff

SystemAdmin - Mon Dec 13 17:10:16 EST 2010
Firstly - creating a version (baseline) of a module every time someone saves the module is going to create many many versions of the module. When DOORS creates a version of a module using its baseline feature, it saves the version as a full copy of the module - not just the delta - a full copy. So this will rapidly gobble up a lot of disk space and increase the amount of time required for overnight database back-ups to complete.

Seems like an unnecessary practice, have certainly never come across a such a need in my experience - can you indicate the rationale behind this request as this might provide some clues for an alternative and more effective way to deliver what is being asked for.

I'm sure that this can be done with triggers but forum participants like Louie Landale, Mathias Mamsch and others who have better expertise than I with triggers may choose to respond.

TooDifficult - Mon Dec 13 19:18:12 EST 2010
I believe that it they want to be able to retrieve any version at will, not just the major revisions.

The problem we have is that when we make the Revision table in a module, the entries are manual.

This means that after editing anything, that particular editor needs to sign off inside that table, giving the date, and his name, and possibly a revision number (1,2,3) if there's a major change.

The users want to reserve baselines for major changes.

I don't know if I made any sense or not lol hope that helped...